It's a bit beyond me where to put

import requests

in order to pass the lint for the sequence of the imports

Hey! This looks interesting, I'm excited to try it out! I noticed the other streamer in the API docs and I am intrigued.

To start off, could you make this in addition to the existing streamer instead of replacing it? I don't think it makes sense to replace the existing streamer yet, especially when the new one has more limited functionality.

Other than that, I think it would be good to get the tests passing. And the Event classes probably don't need to be modified; the event type is implicit in the class definition. Maybe remove that key from the dict before casting it into a class object?

It's a bit beyond me where to put

import requests

in order to pass the lint for the sequence of the imports

You can just run isort tastytrade and the order will be fixed automagically.

• old streamer put back. Switchable using use_legacy flag on create
• Used isort. Is there a way to check this locally before pushing?

Need some help with these last three issues

@Graeme22 @Quenos is there anything I can do to help push this one along? It looks like all of the remaining items were addressed.

Hey! I've been crazy busy the last couple months, but things are calmer now so I should get the chance to tackle this in the next couple days. Thanks for being patient in the meantime!

This is more urgent than I thought, it seems like the old streamer has been moved to delayed quotes! In light of this I don't think there's any reason to keep the old streamer.

it seems like the old streamer has been moved to delayed quotes!

It's still possible to get live quotes using dxFeed with the token and url obtained by the /quote-streamer-tokens endpoint. On the platform, you can switch from dxFeed to dxLink by opening settings and triple-clicking the "Currently using..." text in the general tab. Tastytrade hasn't told me how long they -- or dxFeed -- will support this data feed, but enough users are reporting issues with the websocket stream that I anticipate it will be supported for the platform for the time being.

I would bet that your quotes are being delayed arbitrarily by tastytrade; I had the same issue. You should stop any applications you personally have running using dxFeed, contact tastytrade support to complain about delayed quotes and mention you are not using the old data system, and wait for them to switch you back to live data. From there, you should be able to use dxFeed or dxLink for live data.

If it sounds confusing, arbitrary, and opaque, it's because it is.

As a testing note, wss://tasty-openapi-ws.dxfeed.com/realtime supports fewer event types than wss://tasty-live-ws.dxfeed.com/realtime. Tastytrade has told me this is intentional, and were surprised to hear that the extra events listed below were supported by the live platform feed.

Supported events by both feeds:

• Quote
• Candle
• Trade
• Summary
• Profile

Undocumented events supported only by live feed for platform:

• DailyCandle
• TradeETH
• Greeks
• TimeAndSale
• Underlying
• AnalyticOrder
• OptionSale
• Order
• Series
• Configuration
• Message

As a testing note, wss://tasty-openapi-ws.dxfeed.com/realtime supports fewer event types than wss://tasty-live-ws.dxfeed.com/realtime. Tastytrade has told me this is intentional, and were surprised to hear that the extra events listed below were supported by the live platform feed.

Supported events by both feeds:

• Quote
• Candle
• Trade
• Summary
• Profile

Undocumented events supported only by live feed for platform:

• DailyCandle
• TradeETH
• Greeks
• TimeAndSale
• Underlying
• AnalyticOrder
• OptionSale
• Order
• Series
• Configuration
• Message

This is great stuff, thanks for researching this!

It's still possible to get live quotes using dxFeed with the token and url obtained by the /quote-streamer-tokens endpoint. On the platform, you can switch from dxFeed to dxLink by opening settings and triple-clicking the "Currently using..." text in the general tab. Tastytrade hasn't told me how long they -- or dxFeed -- will support this data feed, but enough users are reporting issues with the websocket stream that I anticipate it will be supported for the platform for the time being.

That's good to know, so we have more time to get these changes integrated then. That said, we should probably get this PR moving along.

To start, can we name the streamers DXFeedStreamer and DXLinkStreamer? And update the DXLink streamer to only support the events that are currently working?

To start, can we name the streamers DXFeedStreamer and DXLinkStreamer? And update the DXLink streamer to only support the events that are currently working?

This will require changes in the documentation as well.

What is still needed here, lost track due to all the comments.

To start, can we name the streamers DXFeedStreamer and DXLinkStreamer? And update the DXLink streamer to only support the events that are currently working?

This to start with